---
title: "FreeBSD 5.0-RELEASE Errata"
sidenav: download
---

++++


        <h3 class="CORPAUTHOR">The FreeBSD Project</h3>

        <p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002,
        2003 by The FreeBSD Documentation Project</p>

        <p class="PUBDATE">$FreeBSD:
        src/release/doc/en_US.ISO8859-1/errata/article.sgml,v 1.38
        2003/04/29 20:39:38 hrs Exp $<br />
        </p>
        <hr />
      </div>

      <blockquote class="ABSTRACT">
        <div class="ABSTRACT">
          <a id="AEN12" name="AEN12"></a>

          <p>This document lists errata items for FreeBSD
          5.0-RELEASE, containing significant information
          discovered after the release or too late in the release
          cycle to be otherwise included in the release
          documentation. This information includes security
          advisories, as well as news relating to the software or
          documentation that could affect its operation or
          usability. An up-to-date version of this document should
          always be consulted before installing this version of
          FreeBSD.</p>

          <p>This errata document for FreeBSD 5.0-RELEASE will be
          maintained until the release of FreeBSD 5.1-RELEASE.</p>
        </div>
      </blockquote>

      <div class="SECT1">
        <hr />

        <h1 class="SECT1"><a id="INTRO" name="INTRO">1
        Introduction</a></h1>

        <p>This errata document contains ``late-breaking news''
        about FreeBSD 5.0-RELEASE. Before installing this version,
        it is important to consult this document to learn about any
        post-release discoveries or problems that may already have
        been found and fixed.</p>

        <p>Any version of this errata document actually distributed
        with the release (for example, on a CDROM distribution)
        will be out of date by definition, but other copies are
        kept updated on the Internet and should be consulted as the
        ``current errata'' for this release. These other copies of
        the errata are located at <a
        href="http://www.FreeBSD.org/releases/"
        target="_top">http://www.FreeBSD.org/releases/</a>, plus
        any sites which keep up-to-date mirrors of this
        location.</p>

        <p>Source and binary snapshots of FreeBSD 5-CURRENT also
        contain up-to-date copies of this document (as of the time
        of the snapshot).</p>

        <p>For a list of all FreeBSD CERT security advisories, see
        <a href="http://www.FreeBSD.org/security/"
        target="_top">http://www.FreeBSD.org/security/</a> or <a
        href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/"
        target="_top">ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/</a>.</p>
      </div>

      <div class="SECT1">
        <hr />

        <h1 class="SECT1"><a id="SECURITY" name="SECURITY">2
        Security Advisories</a></h1>

        <p>Remotely exploitable vulnerabilities in <b
        class="APPLICATION">CVS</b> could allow an attacker to
        execute arbitrary comands on a CVS server. More details can
        be found in security advisory <a
        href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:01.cvs.asc"
         target="_top">FreeBSD-SA-03:01</a>.</p>

        <p>A timing-based attack on <b
        class="APPLICATION">OpenSSL</b>, could allow a very
        powerful attacker access to plaintext under certain
        circumstances. This problem has been corrected in FreeBSD
        5.0-CURRENT with an upgrade to <b
        class="APPLICATION">OpenSSL</b> 0.9.7. On supported
        security fix branches, this problem has been corrected with
        the import of <b class="APPLICATION">OpenSSL</b> 0.9.6i.
        See security advisory <a
        href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:02.openssl.asc"
         target="_top">FreeBSD-SA-03:02</a> for more details.</p>

        <p>It may be possible to recover the shared secret key used
        by the implementation of the ``syncookies'' feature. This
        reduces its effectiveness in dealing with TCP SYN flood
        denial-of-service attacks. Workaround information and fixes
        are given in security advisory <a
        href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:03.syncookies.asc"
         target="_top">FreeBSD-SA-03:03</a>.</p>

        <p>Due to buffer overflows in header parsing in <b
        class="APPLICATION">sendmail</b>, a remote attacker can
        create a specially-crafted message that may cause <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=sendmail&amp;sektion=8&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">sendmail</span>(8)</span></a> to
        execute arbitrary code with the privileges of the user
        running it, typically <tt class="USERNAME">root</tt>. More
        information, including pointers to patches, can be found in
        security advisories <a
        href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:04.sendmail.asc"
         target="_top">FreeBSD-SA-03:04</a> and <a
        href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:07.sendmail.asc"
         target="_top">FreeBSD-SA-03:07</a>.</p>

        <p>The XDR encoder/decoder does incorrect bounds-checking,
        which could allow a remote attacker to cause a
        denial-of-service. For bugfix information, see security
        advisory <a
        href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:05.xdr.asc"
         target="_top">FreeBSD-SA-03:05</a>.</p>

        <p><b class="APPLICATION">OpenSSL</b> has been found
        vulnerable to two recently-disclosed attacks. Information
        on workarounds and patches for supported security branches
        is contained in security advisory <a
        href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:06.openssl.asc"
         target="_top">FreeBSD-SA-03:06</a>.</p>
      </div>

      <div class="SECT1">
        <hr />

        <h1 class="SECT1"><a id="LATE-NEWS" name="LATE-NEWS">3
        Late-Breaking News</a></h1>

        <h4 class="BRIDGEHEAD"><a id="AEN54"
        name="AEN54">GEOM</a></h4>

        <p>The <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&amp;sektion=4&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">geom</span>(4)</span></a>-based disk
        partitioning code in the kernel will not allow an open
        partition to be overwritten. This usually prevents the use
        of <tt class="COMMAND">disklabel -B</tt> to update the boot
        blocks on a disk because the <tt class="LITERAL">a</tt>
        partition overlaps the space where the boot blocks are
        stored. A suggested workaround is to boot from an alternate
        disk, a CDROM, or a fixit floppy.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN61" name="AEN61"><a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=dump&amp;sektion=8&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">dump</span>(8)</span></a></a></h4>

        <p>When using disk media with sector sizes larger than 512
        bytes (for instance, <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=gbde&amp;sektion=4&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">gbde</span>(4)</span></a> encrypted
        disks), the <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=dump&amp;sektion=8&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">dump</span>(8)</span></a> program
        fails to respect the larger sector size and cannot dump the
        partition. One possible workaround is to copy the entire
        file system in raw format and dump the copy. It is, for
        instance, possible to dump a file system stored in a
        regular file:</p>
<pre class="SCREEN">
<tt class="PROMPT">#</tt> <tt
class="USERINPUT"><b>dd if=/dev/ad0s1d.bde of=/junk/ad0.dd bs=1m</b></tt>
<tt class="PROMPT">#</tt> <tt
class="USERINPUT"><b>dump 0f - /junk/ad0.dd | ...</b></tt>
</pre>

        <p>A simpler workaround is to use <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&amp;sektion=1&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">tar</span>(1)</span></a> or <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=cpio&amp;sektion=1&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">cpio</span>(1)</span></a> to make
        backup copies.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN84" name="AEN84"><a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&amp;sektion=4&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">mly</span>(4)</span></a></a></h4>

        <p>Hangs were reported during FreeBSD 5.0 snapshot
        installations when installing to <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&amp;sektion=4&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">mly</span>(4)</span></a>-supported
        RAID arrays, in hardware configurations that appear to work
        fine under FreeBSD 4.7-RELEASE. These problems have been
        corrected in FreeBSD 5.0-CURRENT.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN92"
        name="AEN92">NETNCP/Netware File System Support</a></h4>

        <p>NETNCP and nwfs appear to be as-yet unadapted for KSE,
        and hence not working. These have been fixed in FreeBSD
        5.0-CURRENT.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN94" name="AEN94"><a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&amp;sektion=4&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">iir</span>(4)</span></a>
        controller</a></h4>

        <p>During installation, the <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&amp;sektion=4&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">iir</span>(4)</span></a> controller
        appears to probe correctly, but finds no disk devices.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN102" name="AEN102"><a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&amp;sektion=1&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">truss</span>(1)</span></a> race
        condition</a></h4>

        <p><a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&amp;sektion=1&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">truss</span>(1)</span></a> appears to
        contain a race condition during the start-up of debugging,
        which can result in <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&amp;sektion=1&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">truss</span>(1)</span></a> failing to
        attach to the process before it exists. The symptom is that
        <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&amp;sektion=1&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">truss</span>(1)</span></a> reports
        that it cannot open the <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=procfs&amp;sektion=5&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">procfs</span>(5)</span></a> node
        supporting the process being debugged. A bug also appears
        to exist wherein <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&amp;sektion=1&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">truss</span>(1)</span></a> will hang
        if <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=execve&amp;sektion=2&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">execve</span>(2)</span></a> returns
        <tt class="LITERAL">ENOENT</tt> A further race appears to
        exist in which <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=truss&amp;sektion=1&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">truss</span>(1)</span></a> will
        return ``<tt class="ERRORNAME">PIOCWAIT: Input/output
        error</tt>'' occasionally on startup. The fix for this
        sufficiently changes process execution handling that it has
        been deferred until after 5.0.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN130" name="AEN130">Disk
        Partitioning in Installer</a></h4>

        <p>Some bugs have been reported in <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">sysinstall</span>(8)</span></a> disk
        partitioning. One observed problem on the i386 is that <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
        cannot recalculate the free space left on a disk after
        changing the type of an FDISK-type partition.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN138" name="AEN138">Stale
        Documentation</a></h4>

        <p>In some case, documentation (such as the FAQ or
        Handbook) has not been updated to take into account FreeBSD
        5.0-RELEASE features. Examples of areas where documentation
        is still needed include <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=gbde&amp;sektion=8&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">gbde</span>(8)</span></a> and the new
        ``fast IPsec'' implementation.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN144" name="AEN144">SMB
        File System</a></h4>

        <p>Attempting to unmount smbfs shares may fail with ``<tt
        class="ERRORNAME">Device busy</tt>'' errors even when the
        mount-point is not really busy. A workaround is to keep
        trying to unmount the share until it eventually succeeds.
        This bug has been fixed in 5.0-CURRENT.</p>

        <p>Forcefully unmounting (<tt class="COMMAND">umount
        -f</tt>) smbfs shares may cause a kernel panic. This bug
        has been fixed in 5.0-CURRENT.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN149" name="AEN149"><a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=fstat&amp;sektion=2&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">fstat</span>(2)</span></a></a></h4>

        <p>When called on a connected socket file descriptor, <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=fstat&amp;sektion=2&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">fstat</span>(2)</span></a> is
        supposed to return the number of bytes available to read in
        the <tt class="VARNAME">st_size</tt> member of <tt
        class="VARNAME">struct stat</tt>. However, <tt
        class="VARNAME">st_size</tt> is always erroneously reported
        as <tt class="LITERAL">0</tt> on TCP sockets. This bug has
        been fixed in 5.0-CURRENT.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN161" name="AEN161">Kernel
        Event Queues</a></h4>

        <p>The <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=kqueue&amp;sektion=2&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">kqueue</span>(2)</span></a> <tt
        class="LITERAL">EVFILT_READ</tt> filter erroneously
        indicates that <tt class="LITERAL">0</tt> bytes are
        available to be read on TCP sockets, regardless of the
        number of bytes that are actually available. The <tt
        class="LITERAL">NOTE_LOWAT</tt> flag for <tt
        class="LITERAL">EVFILT_READ</tt> is also broken on TCP
        sockets. This bug has been fixed in 5.0-CURRENT.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN170" name="AEN170">POSIX
        Named Semaphores</a></h4>

        <p>FreeBSD 5.0-RELEASE introduced support for POSIX named
        semaphores but the implementation contains a critical bug
        that causes <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=sem_open&amp;sektion=3&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">sem_open</span>(3)</span></a> to
        incorrectly handle the opening of the same semaphore
        multiple times by the same process, and that causes <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=sem_close&amp;sektion=3&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">sem_close</span>(3)</span></a> to
        crash calling programs. This bug has been fixed in
        5.0-CURRENT.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN178" name="AEN178"><tt
        class="FILENAME">/dev/tty</tt> Permissions</a></h4>

        <p>FreeBSD 5.0-RELEASE has a minor bug in how the
        permissions of <tt class="FILENAME">/dev/tty</tt> are
        handled. This can be triggered by logging in as a non-<tt
        class="USERNAME">root</tt>, non-<tt
        class="GROUPNAME">tty</tt> group user, and using <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=su&amp;sektion=1&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">su</span>(1)</span></a> to switch to
        a second non-<tt class="USERNAME">root</tt>, non-<tt
        class="GROUPNAME">tty</tt> group user. <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=ssh&amp;sektion=1&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">ssh</span>(1)</span></a> will fail
        because it cannot open <tt class="FILENAME">/dev/tty</tt>.
        This bug has been fixed in 5.0-CURRENT.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN193" name="AEN193"><a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=growfs&amp;sektion=8&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">growfs</span>(8)</span></a></a></h4>

        <p><a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=growfs&amp;sektion=8&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">growfs</span>(8)</span></a> no longer
        works on <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=vinum&amp;sektion=4&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">vinum</span>(4)</span></a> volumes
        (and presumably, on <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&amp;sektion=4&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">geom</span>(4)</span></a> entities)
        since these subsystems no longer fake disklabels, but <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=growfs&amp;sektion=8&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">growfs</span>(8)</span></a> insists
        on examining a label.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN210"
        name="AEN210">IPFW</a></h4>

        <p><a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=4&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt
        class="LITERAL">skipto</tt> rules do not work when coupled
        with the <tt class="LITERAL">log</tt> keyword. <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=4&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt
        class="LITERAL">uid</tt> rules also do not work properly.
        These bugs have been fixed in 5.0-CURRENT.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN221"
        name="AEN221">Passwords and <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&amp;sektion=8&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">adduser</span>(8)</span></a></a></h4>

        <p><a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&amp;sektion=8&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">adduser</span>(8)</span></a> does not
        correctly handle setting user passwords containing special
        shell characters. This problem has been corrected in
        5.0-CURRENT.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN229" name="AEN229"><a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&amp;sektion=4&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">xl</span>(4)</span></a></a></h4>

        <p>The <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&amp;sektion=4&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">xl</span>(4)</span></a> driver has a
        timing bug that may cause a kernel panic (or other
        problems) when attempting to configure an interface. This
        bug has been fixed in 5.0-CURRENT.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN237" name="AEN237">ISC
        DHCP</a></h4>

        <p><b class="APPLICATION">ISC DHCP</b> was updated to
        3.0.1rc11. This update was actually a part of FreeBSD
        5.0-RELEASE, but was not documented in the release
        notes.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN240" name="AEN240"><a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&amp;sektion=8&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">amd</span>(8)</span></a>
        Interoperability</a></h4>

        <p>5.0-RELEASE contains some bugs in its non-blocking RPC
        code. The most noticeable side-effect of these bugs was
        that <a
        href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&amp;sektion=8&amp;manpath=FreeBSD+5.0-current">
        <span class="CITEREFENTRY"><span
        class="REFENTRYTITLE">amd</span>(8)</span></a> users were
        not able to mount volumes from a 5.0-RELEASE server. This
        bug has been fixed in 5.0-CURRENT.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN248"
        name="AEN248">nsswitch</a></h4>

        <p>The release note documenting the addition of <b
        class="APPLICATION">nsswitch</b> support gave an incorrect
        name for the old resolver configuration file. It should
        have been listed as <tt
        class="FILENAME">/etc/host.conf</tt>.</p>

        <h4 class="BRIDGEHEAD"><a id="AEN252"
        name="AEN252">Mailman</a></h4>

        <p>Recently the mailing lists were changed from majordomo
        to the currently used Mailman list server. More information
        about using the new mailing lists can be found by visiting
        the <a href="http://www.FreeBSD.org/mailman/listinfo/"
        target="_top">FreeBSD Mailman Info Page</a>.</p>
      </div>
    </div>
    <hr />

    <p align="center"><small>This file, and other release-related
    documents, can be downloaded from <a
    href="http://snapshots.jp.FreeBSD.org/">http://snapshots.jp.FreeBSD.org/</a>.</small></p>

    <p align="center"><small>For questions about FreeBSD, read the
    <a href="http://www.FreeBSD.org/docs.html">documentation</a>
    before contacting &#60;<a
    href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>

    <p align="center"><small><small>All users of FreeBSD 5-CURRENT
    should subscribe to the &#60;<a
    href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>&#62;
    mailing list.</small></small></p>

    <p align="center">For questions about this documentation,
    e-mail &#60;<a
    href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</p>
    <br />
    <br />
++++


